Qcl in rach different from that in other signals

ABSTRACT

A UE determines (a) resources of a PDCCH indicating a PDSCH that contains a random access message or indicating an uplink grant for transmitting a random access message and (b) resources of a second PDCCH. The UE further determines, in a time domain, (a) that the first PDCCH overlaps with the second PDCCH, (b) that the first PDCCH overlaps with a second PDSCH that contains system data or user data and indicated by the second PDCCH, (c) that the first PDSCH overlaps with the second PDCCH, or (d) that the first PDSCH overlaps with the second PDSCH. The UE then determines that monitoring the second PDCCH is an unexpected operation.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefits of U.S. Provisional ApplicationSer. No. 62/631,641, entitled “RACH DESIGN FOR RRC CONNECTED MODE” andfiled on Feb. 17, 2018, which is expressly incorporated by referenceherein in their entirety.

BACKGROUND Field

The present disclosure relates generally to communication systems, andmore particularly, to a random access procedure employed by a userequipment (UE).

Background

The statements in this section merely provide background informationrelated to the present disclosure and may not constitute prior art.

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources. Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example telecommunication standardis 5G New Radio (NR). 5G NR is part of a continuous mobile broadbandevolution promulgated by Third Generation Partnership Project (3GPP) tomeet new requirements associated with latency, reliability, security,scalability (e.g., with Internet of Things (IoT)), and otherrequirements. Some aspects of 5G NR may be based on the 4G Long TermEvolution (LTE) standard. There exists a need for further improvementsin 5G NR technology. These improvements may also be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a UE. The UEdetermines, based on the one or more configurations, (a) resources of afirst physical downlink control channel (PDCCH) indicating a firstphysical downlink shared channel (PDSCH) that contains a random accessmessage or indicating an uplink grant for transmitting a random accessmessage and (b) resources of a second PDCCH. The UE further determines,in a time domain, (a) that the first PDCCH overlaps with the secondPDCCH, (b) that the first PDCCH overlaps with a second PDSCH thatcontains system data or user data and indicated by the second PDCCH, (c)that the first PDSCH overlaps with the second PDCCH, or (d) that thefirst PDSCH overlaps with the second PDSCH. The UE also determines thata first down-link reference signal for monitoring the first PDCCH and asecond down-link reference signal for monitoring the second PDCCH arenot quasi-colocated. The UE then determines that monitoring the secondPDCCH is an unexpected operation.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network.

FIG. 2 is a diagram illustrating a base station in communication with aUE in an access network.

FIG. 3 illustrates an example logical architecture of a distributedaccess network.

FIG. 4 illustrates an example physical architecture of a distributedaccess network.

FIG. 5 is a diagram showing an example of a DL-centric subframe.

FIG. 6 is a diagram showing an example of an UL-centric subframe.

FIG. 7 is a diagram illustrating communications between a base stationand UE.

FIG. 8 is a diagram illustrating a random access procedure of a UE in aconnected state.

FIG. 9 is a diagram illustrating that a UE decodes PDCCHs and PDSCHs ina time slot.

FIG. 10 is a flow chart of a method (process) for monitoring PDCCHs.

FIG. 11 is a conceptual data flow diagram illustrating the data flowbetween different components/means in an exemplary apparatus.

FIG. 12 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, components, circuits,processes, algorithms, etc. (collectively referred to as “elements”).These elements may be implemented using electronic hardware, computersoftware, or any combination thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented as a “processing system” thatincludes one or more processors. Examples of processors includemicroprocessors, microcontrollers, graphics processing units (GPUs),central processing units (CPUs), application processors, digital signalprocessors (DSPs), reduced instruction set computing (RISC) processors,systems on a chip (SoC), baseband processors, field programmable gatearrays (FPGAs), programmable logic devices (PLDs), state machines, gatedlogic, discrete hardware circuits, and other suitable hardwareconfigured to perform the various functionality described throughoutthis disclosure. One or more processors in the processing system mayexecute software. Software shall be construed broadly to meaninstructions, instruction sets, code, code segments, program code,programs, subprograms, software components, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise.

Accordingly, in one or more example embodiments, the functions describedmay be implemented in hardware, software, or any combination thereof. Ifimplemented in software, the functions may be stored on or encoded asone or more instructions or code on a computer-readable medium.Computer-readable media includes computer storage media. Storage mediamay be any available media that can be accessed by a computer. By way ofexample, and not limitation, such computer-readable media can comprise arandom-access memory (RAM), a read-only memory (ROM), an electricallyerasable programmable ROM (EEPROM), optical disk storage, magnetic diskstorage, other magnetic storage devices, combinations of theaforementioned types of computer-readable media, or any other mediumthat can be used to store computer executable code in the form ofinstructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network 100. The wireless communications system(also referred to as a wireless wide area network (WWAN)) includes basestations 102, UEs 104, and a core network 160. The base stations 102 mayinclude macro cells (high power cellular base station) and/or smallcells (low power cellular base station). The macro cells include basestations. The small cells include femtocells, picocells, and microcells.

The base stations 102 (collectively referred to as Evolved UniversalMobile Telecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN)) interface with the core network 160 through backhaul links132 (e.g., S1 interface). In addition to other functions, the basestations 102 may perform one or more of the following functions:transfer of user data, radio channel ciphering and deciphering,integrity protection, header compression, mobility control functions(e.g., handover, dual connectivity), inter-cell interferencecoordination, connection setup and release, load balancing, distributionfor non-access stratum (NAS) messages, NAS node selection,synchronization, radio access network (RAN) sharing, multimediabroadcast multicast service (MBMS), subscriber and equipment trace, RANinformation management (RIM), paging, positioning, and delivery ofwarning messages. The base stations 102 may communicate directly orindirectly (e.g., through the core network 160) with each other overbackhaul links 134 (e.g., X2 interface). The backhaul links 134 may bewired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. There may be overlappinggeographic coverage areas 110. For example, the small cell 102′ may havea coverage area 110′ that overlaps the coverage area 110 of one or moremacro base stations 102. A network that includes both small cell andmacro cells may be known as a heterogeneous network. A heterogeneousnetwork may also include Home Evolved Node Bs (eNBs) (HeNBs), which mayprovide service to a restricted group known as a closed subscriber group(CSG). The communication links 120 between the base stations 102 and theUEs 104 may include uplink (UL) (also referred to as reverse link)transmissions from a UE 104 to a base station 102 and/or downlink (DL)(also referred to as forward link) transmissions from a base station 102to a UE 104. The communication links 120 may use multiple-input andmultiple-output (MIMO) antenna technology, including spatialmultiplexing, beamforming, and/or transmit diversity. The communicationlinks may be through one or more carriers. The base stations 102/UEs 104may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidthper carrier allocated in a carrier aggregation of up to a total of YxMHz (x component carriers) used for transmission in each direction. Thecarriers may or may not be adjacent to each other. Allocation ofcarriers may be asymmetric with respect to DL and UL (e.g., more or lesscarriers may be allocated for DL than for UL). The component carriersmay include a primary component carrier and one or more secondarycomponent carriers. A primary component carrier may be referred to as aprimary cell (PCell) and a secondary component carrier may be referredto as a secondary cell (SCell).

The wireless communications system may further include a Wi-Fi accesspoint (AP) 150 in communication with Wi-Fi stations (STAs) 152 viacommunication links 154 in a 5 GHz unlicensed frequency spectrum. Whencommunicating in an unlicensed frequency spectrum, the STAs 152/AP 150may perform a clear channel assessment (CCA) prior to communicating inorder to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensedfrequency spectrum. When operating in an unlicensed frequency spectrum,the small cell 102′ may employ NR and use the same 5 GHz unlicensedfrequency spectrum as used by the Wi-Fi AP 150. The small cell 102′,employing NR in an unlicensed frequency spectrum, may boost coverage toand/or increase capacity of the access network.

The gNodeB (gNB) 180 may operate in millimeter wave (mmW) frequenciesand/or near mmW frequencies in communication with the UE 104. When thegNB 180 operates in mmW or near mmW frequencies, the gNB 180 may bereferred to as an mmW base station. Extremely high frequency (EHF) ispart of the RF in the electromagnetic spectrum. EHF has a range of 30GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters.Radio waves in the band may be referred to as a millimeter wave. NearmmW may extend down to a frequency of 3 GHz with a wavelength of 100millimeters. The super high frequency (SHF) band extends between 3 GHzand 30 GHz, also referred to as centimeter wave. Communications usingthe mmW/near mmW radio frequency band has extremely high path loss and ashort range. The mmW base station 180 may utilize beamforming 184 withthe UE 104 to compensate for the extremely high path loss and shortrange.

The core network 160 may include a Mobility Management Entity (MME) 162,other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast MulticastService (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be incommunication with a Home Subscriber Server (HSS) 174. The MME 162 isthe control node that processes the signaling between the UEs 104 andthe core network 160. Generally, the MME 162 provides bearer andconnection management. All user Internet protocol (IP) packets aretransferred through the Serving Gateway 166, which itself is connectedto the PDN Gateway 172. The PDN Gateway 172 provides UE IP addressallocation as well as other functions. The PDN Gateway 172 and the BM-SC170 are connected to the IP Services 176. The IP Services 176 mayinclude the Internet, an intranet, an IP Multimedia Subsystem (IMS), aPS Streaming Service (PSS), and/or other IP services. The BM-SC 170 mayprovide functions for MBMS user service provisioning and delivery. TheBM-SC 170 may serve as an entry point for content provider MBMStransmission, may be used to authorize and initiate MBMS Bearer Serviceswithin a public land mobile network (PLMN), and may be used to scheduleMBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMStraffic to the base stations 102 belonging to a Multicast BroadcastSingle Frequency Network (MBSFN) area broadcasting a particular service,and may be responsible for session management (start/stop) and forcollecting eMBMS related charging information.

The base station may also be referred to as a gNB, Node B, evolved NodeB (eNB), an access point, a base transceiver station, a radio basestation, a radio transceiver, a transceiver function, a basic serviceset (BSS), an extended service set (ESS), or some other suitableterminology. The base station 102 provides an access point to the corenetwork 160 for a UE 104. Examples of UEs 104 include a cellular phone,a smart phone, a session initiation protocol (SIP) phone, a laptop, apersonal digital assistant (PDA), a satellite radio, a globalpositioning system, a multimedia device, a video device, a digital audioplayer (e.g., MP3 player), a camera, a game console, a tablet, a smartdevice, a wearable device, a vehicle, an electric meter, a gas pump, atoaster, or any other similar functioning device. Some of the UEs 104may be referred to as IoT devices (e.g., parking meter, gas pump,toaster, vehicles, etc.). The UE 104 may also be referred to as astation, a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a wireless communications device, a remote device, amobile subscriber station, an access terminal, a mobile terminal, awireless terminal, a remote terminal, a handset, a user agent, a mobileclient, a client, or some other suitable terminology.

FIG. 2 is a block diagram of a base station 210 in communication with aUE 250 in an access network. In the DL, IP packets from the core network160 may be provided to a controller/processor 275. Thecontroller/processor 275 implements layer 3 and layer 2 functionality.Layer 3 includes a radio resource control (RRC) layer, and layer 2includes a packet data convergence protocol (PDCP) layer, a radio linkcontrol (RLC) layer, and a medium access control (MAC) layer. Thecontroller/processor 275 provides RRC layer functionality associatedwith broadcasting of system information (e.g., MIB, SIBs), RRCconnection control (e.g., RRC connection paging, RRC connectionestablishment, RRC connection modification, and RRC connection release),inter radio access technology (RAT) mobility, and measurementconfiguration for UE measurement reporting; PDCP layer functionalityassociated with header compression/decompression, security (ciphering,deciphering, integrity protection, integrity verification), and handoversupport functions; RLC layer functionality associated with the transferof upper layer packet data units (PDUs), error correction through ARQ,concatenation, segmentation, and reassembly of RLC service data units(SDUs), re-segmentation of RLC data PDUs, and reordering of RLC dataPDUs; and MAC layer functionality associated with mapping betweenlogical channels and transport channels, multiplexing of MAC SDUs ontotransport blocks (TBs), demultiplexing of MAC SDUs from TBs, schedulinginformation reporting, error correction through HARQ, priority handling,and logical channel prioritization.

The transmit (TX) processor 216 and the receive (RX) processor 270implement layer 1 functionality associated with various signalprocessing functions. Layer 1, which includes a physical (PHY) layer,may include error detection on the transport channels, forward errorcorrection (FEC) coding/decoding of the transport channels,interleaving, rate matching, mapping onto physical channels,modulation/demodulation of physical channels, and MIMO antennaprocessing. The TX processor 216 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from a channelestimator 274 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe UE 250. Each spatial stream may then be provided to a differentantenna 220 via a separate transmitter 218TX. Each transmitter 218TX maymodulate an RF carrier with a respective spatial stream fortransmission.

At the UE 250, each receiver 254RX receives a signal through itsrespective antenna 252. Each receiver 254RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 256. The TX processor 268 and the RX processor 256implement layer 1 functionality associated with various signalprocessing functions. The RX processor 256 may perform spatialprocessing on the information to recover any spatial streams destinedfor the UE 250. If multiple spatial streams are destined for the UE 250,they may be combined by the RX processor 256 into a single OFDM symbolstream. The RX processor 256 then converts the OFDM symbol stream fromthe time-domain to the frequency domain using a Fast Fourier Transform(FFT). The frequency domain signal comprises a separate OFDM symbolstream for each subcarrier of the OFDM signal. The symbols on eachsubcarrier, and the reference signal, are recovered and demodulated bydetermining the most likely signal constellation points transmitted bythe base station 210. These soft decisions may be based on channelestimates computed by the channel estimator 258. The soft decisions arethen decoded and deinterleaved to recover the data and control signalsthat were originally transmitted by the base station 210 on the physicalchannel. The data and control signals are then provided to thecontroller/processor 259, which implements layer 3 and layer 2functionality.

The controller/processor 259 can be associated with a memory 260 thatstores program codes and data. The memory 260 may be referred to as acomputer-readable medium. In the UL, the controller/processor 259provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing to recover IP packets from the core network 160. Thecontroller/processor 259 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DLtransmission by the base station 210, the controller/processor 259provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto TBs,demultiplexing of MAC SDUs from TBs, scheduling information reporting,error correction through HARQ, priority handling, and logical channelprioritization.

Channel estimates derived by a channel estimator 258 from a referencesignal or feedback transmitted by the base station 210 may be used bythe TX processor 268 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the TX processor 268 may be provided to different antenna252 via separate transmitters 254TX. Each transmitter 254TX may modulatean RF carrier with a respective spatial stream for transmission. The ULtransmission is processed at the base station 210 in a manner similar tothat described in connection with the receiver function at the UE 250.Each receiver 218RX receives a signal through its respective antenna220. Each receiver 218RX recovers information modulated onto an RFcarrier and provides the information to a RX processor 270.

The controller/processor 275 can be associated with a memory 276 thatstores program codes and data. The memory 276 may be referred to as acomputer-readable medium. In the UL, the controller/processor 275provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover IP packets from the UE 250. IP packets from thecontroller/processor 275 may be provided to the core network 160. Thecontroller/processor 275 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

New radio (NR) may refer to radios configured to operate according to anew air interface (e.g., other than Orthogonal Frequency DivisionalMultiple Access (OFDMA)-based air interfaces) or fixed transport layer(e.g., other than Internet Protocol (IP)). NR may utilize OFDM with acyclic prefix (CP) on the uplink and downlink and may include supportfor half-duplex operation using time division duplexing (TDD). NR mayinclude Enhanced Mobile Broadband (eMBB) service targeting widebandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting highcarrier frequency (e.g. 60 GHz), massive MTC (mMTC) targetingnon-backward compatible MTC techniques, and/or mission criticaltargeting ultra-reliable low latency communications (URLLC) service.

A single component carrier bandwidth of 100 MHZ may be supported. In oneexample, NR resource blocks (RBs) may span 12 sub-carriers with asub-carrier bandwidth of 60 kHz over a 0.125 ms duration or a bandwidthof 15 kHz over a 0.5 ms duration. Each radio frame may consist of 20 or80 subframes (or NR slots) with a length of 10 ms. Each subframe mayindicate a link direction (i.e., DL or UL) for data transmission and thelink direction for each subframe may be dynamically switched. Eachsubframe may include DL/UL data as well as DL/UL control data. UL and DLsubframes for NR may be as described in more detail below with respectto FIGS. 5 and 6.

The NR RAN may include a central unit (CU) and distributed units (DUs).A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point(TRP), access point (AP)) may correspond to one or multiple BSs. NRcells can be configured as access cells (ACells) or data only cells(DCells). For example, the RAN (e.g., a central unit or distributedunit) can configure the cells. DCells may be cells used for carrieraggregation or dual connectivity and may not be used for initial access,cell selection/reselection, or handover. In some cases DCells may nottransmit synchronization signals (SS) in some cases DCells may transmitSS. NR BSs may transmit downlink signals to UEs indicating the celltype. Based on the cell type indication, the UE may communicate with theNR BS. For example, the UE may determine NR BSs to consider for cellselection, access, handover, and/or measurement based on the indicatedcell type.

FIG. 3 illustrates an example logical architecture 300 of a distributedRAN, according to aspects of the present disclosure. A 5G access node306 may include an access node controller (ANC) 302. The ANC may be acentral unit (CU) of the distributed RAN 300. The backhaul interface tothe next generation core network (NG-CN) 304 may terminate at the ANC.The backhaul interface to neighboring next generation access nodes(NG-ANs) may terminate at the ANC. The ANC may include one or more TRPs308 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs,or some other term). As described above, a TRP may be usedinterchangeably with “cell.”

The TRPs 308 may be a distributed unit (DU). The TRPs may be connectedto one ANC (ANC 302) or more than one ANC (not illustrated). Forexample, for RAN sharing, radio as a service (RaaS), and servicespecific AND deployments, the TRP may be connected to more than one ANC.A TRP may include one or more antenna ports. The TRPs may be configuredto individually (e.g., dynamic selection) or jointly (e.g., jointtransmission) serve traffic to a UE.

The local architecture of the distributed RAN 300 may be used toillustrate fronthaul definition. The architecture may be defined thatsupport fronthauling solutions across different deployment types. Forexample, the architecture may be based on transmit network capabilities(e.g., bandwidth, latency, and/or jitter). The architecture may sharefeatures and/or components with LTE. According to aspects, the nextgeneration AN (NG-AN) 310 may support dual connectivity with NR. TheNG-AN may share a common fronthaul for LTE and NR.

The architecture may enable cooperation between and among TRPs 308. Forexample, cooperation may be preset within a TRP and/or across TRPs viathe ANC 302. According to aspects, no inter-TRP interface may beneeded/present.

According to aspects, a dynamic configuration of split logical functionsmay be present within the architecture of the distributed RAN 300. ThePDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.

FIG. 4 illustrates an example physical architecture of a distributed RAN400, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 402 may host core network functions. The C-CU may becentrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.A centralized RAN unit (C-RU) 404 may host one or more ANC functions.Optionally, the C-RU may host core network functions locally. The C-RUmay have distributed deployment. The C-RU may be closer to the networkedge. A distributed unit (DU) 406 may host one or more TRPs. The DU maybe located at edges of the network with radio frequency (RF)functionality.

FIG. 5 is a diagram 500 showing an example of a DL-centric subframe. TheDL-centric subframe may include a control portion 502. The controlportion 502 may exist in the initial or beginning portion of theDL-centric subframe. The control portion 502 may include variousscheduling information and/or control information corresponding tovarious portions of the DL-centric subframe. In some configurations, thecontrol portion 502 may be a physical DL control channel (PDCCH), asindicated in FIG. 5. The DL-centric subframe may also include a DL dataportion 504. The DL data portion 504 may sometimes be referred to as thepayload of the DL-centric subframe. The DL data portion 504 may includethe communication resources utilized to communicate DL data from thescheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE).In some configurations, the DL data portion 504 may be a physical DLshared channel (PDSCH).

The DL-centric subframe may also include a common UL portion 506. Thecommon UL portion 506 may sometimes be referred to as an UL burst, acommon UL burst, and/or various other suitable terms. The common ULportion 506 may include feedback information corresponding to variousother portions of the DL-centric subframe. For example, the common ULportion 506 may include feedback information corresponding to thecontrol portion 502. Non-limiting examples of feedback information mayinclude an ACK signal, a NACK signal, a HARQ indicator, and/or variousother suitable types of information. The common UL portion 506 mayinclude additional or alternative information, such as informationpertaining to random access channel (RACH) procedures, schedulingrequests (SRs), and various other suitable types of information.

As illustrated in FIG. 5, the end of the DL data portion 504 may beseparated in time from the beginning of the common UL portion 506. Thistime separation may sometimes be referred to as a gap, a guard period, aguard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the subordinate entity (e.g., UE)) to UL communication(e.g., transmission by the subordinate entity (e.g., UE)). One ofordinary skill in the art will understand that the foregoing is merelyone example of a DL-centric subframe and alternative structures havingsimilar features may exist without necessarily deviating from theaspects described herein.

FIG. 6 is a diagram 600 showing an example of an UL-centric subframe.The UL-centric subframe may include a control portion 602. The controlportion 602 may exist in the initial or beginning portion of theUL-centric subframe. The control portion 602 in FIG. 6 may be similar tothe control portion 502 described above with reference to FIG. 5. TheUL-centric subframe may also include an UL data portion 604. The UL dataportion 604 may sometimes be referred to as the pay load of theUL-centric subframe. The UL portion may refer to the communicationresources utilized to communicate UL data from the subordinate entity(e.g., UE) to the scheduling entity (e.g., UE or BS). In someconfigurations, the control portion 602 may be a physical DL controlchannel (PDCCH).

As illustrated in FIG. 6, the end of the control portion 602 may beseparated in time from the beginning of the UL data portion 604. Thistime separation may sometimes be referred to as a gap, guard period,guard interval, and/or various other suitable terms. This separationprovides time for the switch-over from DL communication (e.g., receptionoperation by the scheduling entity) to UL communication (e.g.,transmission by the scheduling entity). The UL-centric subframe may alsoinclude a common UL portion 606. The common UL portion 606 in FIG. 6 maybe similar to the common UL portion 606 described above with referenceto FIG. 6. The common UL portion 606 may additionally or alternativelyinclude information pertaining to channel quality indicator (CQI),sounding reference signals (SRSs), and various other suitable types ofinformation. One of ordinary skill in the art will understand that theforegoing is merely one example of an UL-centric subframe andalternative structures having similar features may exist withoutnecessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) maycommunicate with each other using sidelink signals. Real-worldapplications of such sidelink communications may include public safety,proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V)communications, Internet of Everything (IoE) communications, IoTcommunications, mission-critical mesh, and/or various other suitableapplications. Generally, a sidelink signal may refer to a signalcommunicated from one subordinate entity (e.g., UE1) to anothersubordinate entity (e.g., UE2) without relaying that communicationthrough the scheduling entity (e.g., UE or BS), even though thescheduling entity may be utilized for scheduling and/or controlpurposes. In some examples, the sidelink signals may be communicatedusing a licensed spectrum (unlike wireless local area networks, whichtypically use an unlicensed spectrum).

FIG. 7 is a diagram 700 illustrating communications between a basestation 702 and a UE 704. The base station 702 may operates antennaports 722-1 to 722-N. The base station 702 provides transmitter sidebeams 726-1 to 726-N at different directions. The UE 704 may use arandom access procedure to gain access to a cell of the base station702. In this example, to facilitate a UE to perform the random accessprocedure, the base station 702 transmits a set of synchronizationsignal blocks (SSBs) including SSBs 732-1 to 732-N, which are associatedwith the transmitter side beams 726-1 to 726-N, respectively. Morespecifically, the Primary Synchronization Signal (PSS) and the SecondarySynchronization Signal (SSS), together with the Physical BroadcastChannel (PBCH), are jointly referred to as an SSB. Each of the SSBs732-1 to 732-N may include one or more Demodulation Reference Signals(DMRSs) for PBCH. The DMRSs are intended for channel estimation at a UEas part of coherent demodulation.

Further, the base station 702 may transmit CSI-RS sets 734-1 to 734-Nthat are specific to the UE 704 by using the transmitter side beams726-1 to 726-N, respectively. A CSI-RS is used by the UE to estimate thechannel and report channel state information (CSI) to the base station.A CSI-RS is configured on a per-device basis.

In certain configurations, the UE 704 may select one of the transmitterside beams 726-1 to 726-N randomly or based on a rule for deriving acorresponding preamble sequence used in the random access procedure. Incertain configurations, the UE 704 may adjust the direction of areceiver side beam 728 to detect and measure the SSBs 732-1 to 732-N orthe CSI-RS sets 734-1 to 734-N. Based on the detection and/ormeasurements (e.g., SNR measurements), the UE 704 may select a directionof the receiver side beam 728 and one of the transmitter side beams726-1 to 726-N for deriving a corresponding preamble sequence used inthe random access procedure.

In one example, the UE 704 may select the transmitter side beam 726-2for deriving an associated preamble sequence for use in the randomaccess procedure. More specifically, the UE 704 is configured with oneor more random access resources associated with each the SSBs 732-1 to732-N and/or one or more random access resources associated with eachthe CSI-RS sets 734-1 to 734-N.

Accordingly, the UE 704 may select a random access resource associatedwith the down-link reference signal (e.g., SSB or CSI-RS) of thetransmitter side beam 726-2 (i.e., the selected one of the transmitterside beams 726-1 to 726-N). Subsequently, the UE 704 sends a preamblesequence 752 to the base station 702 through the receiver side beam 728(by assuming a corresponding UE transmit beam can be derived from thereceiver side beam 828) on the selected random access resource. Based onthe location of the random access resource in time domain and frequencydomain, the base station 702 can determine the transmitter side beamselected by the UE 704.

Subsequently, the base station 702 and the UE 704 can further completethe random access procedure such that the base station 702 and the UE704 can communicate through the transmitter side beam 726-2 and thereceiver side beam 728. As such, the UE 704 is in a connected state(e.g., RRC CONNECTED) with the base station 702. The base station 702may use the transmitter side beam 726-2 to transmit to the UE 704 aPDCCH 742, a PDSCH 744, and associated DMRSs 746.

FIG. 8 is diagram 800 illustrating a random access procedure of a UE ina connected state. In certain circumstances, the UE 704, although in aconnected state, may need to conduct the random access procedure withthe base station 702 or another base station. In this example, asdescribed supra referring to FIG. 7, the UE 704 is connected to the basestation 702. The UE 704 may receive a request (e.g., a PDCCH order) fromthe base station 702 to initiate a random access procedure again. The UE704 may detect an up-link data arrival without up-link synchronizationand, thus, may conduct the random access procedure with the base station702. The UE 704 may detect a down-link data arrival without up-linksynchronization and, thus, may conduct the random access procedure withthe base station 702 and, thus, may conduct the random access procedurewith the base station 702. The UE 704 may decide to recover a beam and,thus, may conduct the random access procedure with the base station 702.The UE 704 may be handed over from the base station 702 to another basestation and, thus, may conduct the random access procedure with theother base station.

In this example, at procedure 802, the base station 702 sends a PDCCHorder to the UE 704. In particular, the PDCCH order may be transmittedby using the transmitter side beam 726-2. Accordingly, upon received thePDCCH order, at procedure 803, the UE 704 initiates a random accessprocedure while in a connected state. In another example, the UE 704 maydetect a beam failure and internally generates a beam failure recoveryrequest. Accordingly, the UE 704 can also initiate a random accessprocedure while in a connected state. At procedure 804, as describedsupra, the base station 702 sends the SSBs 732-1 to 732-N and/or theCSI-RS sets 734-1 to 734-N associated with the transmitter side beams726-1 to 726-N, respectively. The UE 704 may detect some or all of theSSBs 732-1 to 732-N. Note that procedure 804 can also take place beforeprocedure 802.

At procedure 806, as described supra, in certain configurations, the UE704 may select one of the transmitter side beams 726-1 to 726-N randomlyor based on the measurement result. As an example, the base station 702may select the transmitter side beam 726-1 for deriving an associatedpreamble sequence 752 for use in the random access procedure.

Accordingly, the base station 702 may use a correspondent beam of thetransmitter side beam 726-2 to receive the preamble sequence 752, whichis transmitted on a random access resource associated with the down-linkreference signals of the transmitter side beam 726-1. The UE 704determines a timing advance (TA) for the UE 704 based on the preamblesequence 752 received through the transmitter side beam 726-2.

As such, the base station 702 may receive the preamble sequence 752 onthe transmitter side beam 726-2. The network of the base station 702 canalso determine that the preamble sequence 752 was transmitted at arandom access resource associated with the SSB 732-2 and/or the CSI-RSset 734-2 of the transmitter side beam 726-2. As such, the networklearns that the UE 704 selected the transmitter side beam 726-2.

At procedure 810, the base station 702 (under the control of thenetwork) generates a random-access response (RAR). The RAR may includeinformation about the preamble sequence 752 the network detected and forwhich the response is valid, a TA calculated by the network based on thepreamble sequence receive timing, a scheduling grant indicatingresources the UE 704 will use for the transmission of the subsequentmessage, and/or a temporary identity, the TC-RNTI, used for furthercommunication between the device and the network.

At procedure 812, the base station 702 transmits a PDCCH schedulingcommand for scheduling transmission of the RAR by using the transmitterside beam 726-2. Accordingly, DMRS of the PDCCH scheduling command andDMRS of the PDCCH order at procedure 802 are quasi-colocated. Further,the PDCCH scheduling command may be scrambled by a cell radio networktemporary identifier (C-RNTI) of the UE 704, which is known to thenetwork. Further, as described supra, the UE 704 is in a connectedstate. The serving beam from the base station 702 to the UE 704 may bethe transmitter side beam 726-1. At or about the same time the basestation 702 sends the PDCCH scheduling command for schedulingtransmission of the RAR on the transmitter side beam 726-2, the basestation 702 may also send a PDCCH on the transmitter side beam 726-1 forscheduling a PDSCH carrying user data.

At procedure 814, the base station 702 transmits the RAR to the UE 704on the transmitter side beam 726-2. The RAR may be transmitted in aconventional downlink PDSCH. As such, the random access procedurecompletes for the UE 704, which is in a connected state.

FIG. 9 is a diagram 900 illustrating that a UE decodes PDCCHs and PDSCHsin a time slot. The UE 704 receives CORESET configurations and searchspace set configurations from the base station 702 via UE-specific RRCsignaling. Based on those configurations, the UE 704 can determine PDCCHcommon search space sets and UE specific PDCCH search space setsassigned to the UE 704. Further, the CORESET configuration contains afield specifying QCL association of the serving beam (e.g., thetransmitter side beam 726-1 in this example). In particular, the fieldspecifies an antenna port quasi-colocations, from a set of antenna portquasi-colocations provided by higher layer parameter “TCI-StatesPDCCH,”indicating quasi co-location information of the DM-RS antenna port forPDCCH reception.

Further, a PDCCH common search space set may be a Type 0 PDCCH commonsearch space set, which may be configured by parameter“pdcch-ConfigSIB1” in MIB or by parameter “searchSpaceSIB1” inPDCCH-ConfigCommon or by parameter “searchSpaceZero” inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI.

A PDCCH common search space set may be a Type 0A PDCCH common searchspace set, which is configured by “searchSpaceOtherSystemInformation” inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI.

A PDCCH common search space set may be a Type 1 PDCCH common searchspace set, which is configured by “ra-SearchSpace” in PDCCH-ConfigCommonfor a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI.

A PDCCH common search space set may be a Type 2 PDCCH common searchspace set, which is configured by “pagingSearchSpace” inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI.

A PDCCH common search space set may be a Type 3 PDCCH common searchspace set, which is configured by “SearchSpace” in PDCCH-Config with“searchSpaceType=common” for DCI formats with CRC scrambled by INT-RNTI,SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI and, only forthe primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s).

A UE specific PDCCH search space set may be configured by “SearchSpace”in PDCCH-Config with “searchSpaceType=ue-Specific” for DCI formats withCRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s).

In this example, the UE 704 is allocated, among other search space sets,a search space set 932 and a search space set 934 in a slot 912.Further, based on the configurations, the UE 704 determines that thesearch space set 932 is a Type 1 PDCCH common search space set and thatthe search space set 934 is a Type 0/0A/2/3 PDCCH common search spaceset or a UE specific PDCCH search space set.

As described supra referring to FIGS. 7-8, at procedure 806, the UE 704selected down-link reference signals of the transmitter side beam 726-2.At procedure 808, the UE 704 indicates the selected down-link referencesignals to the base station 702. Accordingly, the UE 704 needs tomonitor the search space set 932 on the transmitter side beam 726-2 todetect a PDCCH. The PDCCH may indicate resources of a PDSCH 962, whichmay be used to carry an RAR (as described supra referring to procedure814). In other circumstances, the PDCCH may indicate a PDSCH that carrya downlink random access message for contention resolution, where thePDCCH is scrambled by either Temporary C-RNTI (TC-RNTI) or C-RNTI. Inother circumstances, the PDCCH may carry an uplink grant for an uplinkrandom access message that indicates the identity of the UE 704, wherethe PDCCH is scrambled by Temporary C-RNTI (TC-RNTI).

Further, the UE 704 may also monitor the search space set 934 on thetransmitter side beam 726-1, which is the serving beam, to detect aPDCCH scheduling a PDSCH that carries user data or system data. In thisexample, the search space set 934 may contain a PDCCH indicating a PDSCH964.

In this example, the UE 704 determines, e.g., based on thequasi-colocation information in the CORESET configuration, that thedown-link reference signal of the transmitter side beam 726-2 is notquasi-colocated with the DMRS associated with the transmitter side beam726-1.

In this example, the UE 704 further determines that the search space set932 and the search space set 932 overlap with each other in the timedomain. More specifically, both the search space set 932 and the searchspace set 934 occupies a symbol period 917.

In this situation, the UE 704 determines that an unexpected event hasoccurred. The UE 704 is not expected to monitor PDCCHs on thetransmitter side beam 726-1 and the transmitter side beam 726-2simultaneously. Accordingly, the UE 704 may choose to only monitor andblind-decode the search space set 932 to complete the random accessprocedure, but not monitor or blind-decode the search space set 934.

In a second example, the search space set 932 and the search space set934 may not overlap in the time domain. Therefore, the UE 704 mayperform blind decoding on the search space set 932 and the search spaceset 934. In this example, the search space set 932 has a PDCCH carryingDCI scrambled by a RA-RNTI or a TC-RNTI and indicating the PDSCH 962.The search space set 934 has a PDCCH carrying DCI scrambled by RNTIother than a RA-RNTI or a TC-RNTI and indicating the PDSCH 964.

Based on the DCI carried in the search space set 932 and the searchspace set 934, the UE 704 determines resources of the PDSCH 962 and thePDSCH 964. In this example, the UE 704 further determines that the PDSCH962 and the PDSCH 964 overlap. For example, both the PDSCH 962 and thePDSCH 964 occupy the symbol period 918.

In this situation, the UE 704 determines that an unexpected event hasoccurred. The UE 704 is not expected to decode PDSCHs on the transmitterside beam 726-1 and the transmitter side beam 726-2 simultaneously.Accordingly, the UE 704 may choose to only decode the PDSCH 962 tocomplete the random access procedure, but not to decode the PDSCH 964.

In a third example, the search space set 932 overlaps with the PDSCH 964(not shown in FIG. 9). In this situation, the UE 704 determines that anunexpected event has occurred. The UE 704 is not expected to monitor aPDCCH on the transmitter side beam 726-1 and decode a PDSCH on thetransmitter side beam 726-2 simultaneously. Accordingly, the UE 704 maychoose to only monitor the search space set 932 to complete the randomaccess procedure, but not to decode the PDSCH 964.

In a fourth example, the search space set 934 overlaps with the PDSCH962 (not shown in FIG. 9). In this situation, the UE 704 determines thatan unexpected event has occurred. The UE 704 is not expected to monitora PDCCH on the transmitter side beam 726-2 and decode a PDSCH on thetransmitter side beam 726-1 simultaneously. Accordingly, the UE 704 maychoose to decode the PDSCH 962 to complete the random access procedure,but not to monitor the search space set 934.

FIG. 10 is a flow chart 1000 of a method (process) for monitoringPDCCHs. The method may be performed by a UE (e.g., the UE 704, theapparatus 1102, and the apparatus 1102′). At operation 1002, the UEreceives one or more configurations (e.g., a CORESET configuration, asearch space set configuration) from a base station via signaling in aconnected state. At operation 1004, the UE determines that a randomaccess event (e.g., the PDCCH order in procedure 802) has occurred inthe connected state. At operation 1006, the UE selects a down-linkreference signal (e.g., the SSB 732-2, the CSI-RS set 734-2) transmittedfrom the base station and that is not quasi-colocated with a servingbeam (e.g., the transmitter side beam 726-1) of from the base station tothe UE. At operation 1008, the UE transmits a preamble sequence (e.g.,the preamble sequence 752) to the base station using random accesssources indicating the selected down-link reference signal.

At operation 1010, the UE determines, based on the one or moreconfigurations, (a) resources of a first PDCCH (e.g., the PDCCH in thesearch space set 932) indicating a first PDSCH (e.g., the PDSCH 962)that contains a random access message (e.g., the RAR in procedure 814)or indicating an uplink grant for transmitting a random access messageand (b) resources of a second PDCCH (e.g., the PDCCH in the search spaceset 934).

At operation 1012, the UE determines, in a time domain, (a) that thefirst PDCCH overlaps with the second PDCCH, (b) that the first PDCCHoverlaps with a second PDSCH that contains system data or user data andindicated by the second PDCCH, (c) that the first PDSCH overlaps withthe second PDCCH, or (d) that the first PDSCH overlaps with the secondPDSCH.

At operation 1014, the UE determines that a first down-link referencesignal (e.g., the SSB 732-2, CSI-RS set 734-2) for monitoring the firstPDCCH and a second down-link reference signal (e.g., DMRS on thetransmitter side beam 726-1) for monitoring the second PDCCH are notquasi-colocated. In certain configurations, the first down-linkreference signal is a channel state information reference signal or asynchronization signal block. At operation 1016, the UE determines thatmonitoring the second PDCCH is an unexpected operation. At operation1018, the UE receives, from the base station, the random access messageon the second PDSCH on a beam that is different from the serving beam.

In certain circumstances, the first PDCCH overlaps with the secondPDCCH. The UE monitors the first PDCCH. The UE refrains from monitoringthe second PDCCH. In certain circumstances, the first PDCCH overlapswith the second PDSCH. The UE monitors the first PDCCH. The UE refrainsfrom decoding the second PDSCH. In certain circumstances, the firstPDSCH overlaps with the second PDCCH. The UE decodes the first PDSCH.The UE refrains from monitoring the second PDCCH. In certaincircumstances, the first PDSCH overlaps with the second PDSCH. The UEdecodes the first PDSCH. The UE refrains from decoding the second PDSCH.

In certain configurations, the first PDCCH is scrambled with a randomaccess radio network temporary identifier (RA-RNTI) and the second PDCCHis scrambled with a radio network temporary identifier (RNTI) other thanthe RA-RNTI. In certain configurations, the first PDCCH is scrambledwith a temporary cell radio network temporary identifier (TC-RNTI) andthe second PDCCH is scrambled with a radio network temporary identifier(RNTI) other than the TC-RNTI. In certain configurations, the firstPDCCH is located in a Type 1 PDCCH common search space set. The secondPDCCH is located in a Type 0 PDCCH common search space set, a Type 0APDCCH common search space set, a Type 2 PDCCH common search space set, aType 3 PDCCH common search space set, or a UE specific PDCCH searchspace set.

FIG. 11 is a conceptual data flow diagram 1100 illustrating the dataflow between different components/means in an exemplary apparatus 1102.The apparatus 1102 may be a UE. The apparatus 1102 includes a receptioncomponent 1104, a configuration component 1106, a decoding component1108, a RA component 1112, and a transmission component 1110.

The configuration component 1106 receives one or more configurationsfrom a base station 1150 via signaling in a connected state. The RAcomponent 1112 determines that a random access event has occurred in theconnected state. The RA component 1112 selects a down-link referencesignal transmitted from the base station and that is not quasi-colocatedwith a serving beam of from the base station to the UE. The RA component1112 transmits a preamble sequence to the base station using randomaccess sources indicating the selected down-link reference signal.

The decoding component 1108 determines, based on the one or moreconfigurations, (a) resources of a first physical downlink controlchannel (PDCCH) indicating a first physical downlink shared channel(PDSCH) that contains a random access message or indicating an uplinkgrant for transmitting a random access message and (b) resources of asecond PDCCH.

The decoding component 1108 determines, in a time domain, (a) that thefirst PDCCH overlaps with the second PDCCH, (b) that the first PDCCHoverlaps with a second PDSCH that contains system data or user data andindicated by the second PDCCH, (c) that the first PDSCH overlaps withthe second PDCCH, or (d) that the first PDSCH overlaps with the secondPDSCH.

The decoding component 1108 determines that a first down-link referencesignal for monitoring the first PDCCH and a second down-link referencesignal for monitoring the second PDCCH are not quasi-colocated. Incertain configurations, the first down-link reference signal is achannel state information reference signal or a synchronization signalblock. The decoding component 1108 determines that monitoring the secondPDCCH is an unexpected operation. The RA component 1112 receives, fromthe base station, the random access message on the second PDSCH on abeam that is different from the serving beam.

In certain circumstances, the first PDCCH overlaps with the secondPDCCH. The UE monitors the first PDCCH. The UE refrains from monitoringthe second PDCCH. In certain circumstances, the first PDCCH overlapswith the second PDSCH. The UE monitors the first PDCCH. The UE refrainsfrom decoding the second PDSCH. In certain circumstances, the firstPDSCH overlaps with the second PDCCH. The UE decodes the first PDSCH.The UE refrains from monitoring the second PDCCH. In certaincircumstances, the first PDSCH overlaps with the second PDSCH. The UEdecodes the first PDSCH. The UE refrains from decoding the second PDSCH.

In certain configurations, the first PDCCH is scrambled with a randomaccess radio network temporary identifier (RA-RNTI) and the second PDCCHis scrambled with a radio network temporary identifier (RNTI) other thanthe RA-RNTI. In certain configurations, the first PDCCH is scrambledwith a temporary cell radio network temporary identifier (TC-RNTI) andthe second PDCCH is scrambled with a radio network temporary identifier(RNTI) other than the TC-RNTI. In certain configurations, the firstPDCCH is located in a Type 1 PDCCH common search space set. The secondPDCCH is located in a Type 0 PDCCH common search space set, a Type 0APDCCH common search space set, a Type 2 PDCCH common search space set, aType 3 PDCCH common search space set, or a UE specific PDCCH searchspace set.

FIG. 12 is a diagram 1200 illustrating an example of a hardwareimplementation for an apparatus 1102′ employing a processing system1214. The apparatus 1102′ may be a UE. The processing system 1214 may beimplemented with a bus architecture, represented generally by a bus1224. The bus 1224 may include any number of interconnecting buses andbridges depending on the specific application of the processing system1214 and the overall design constraints. The bus 1224 links togethervarious circuits including one or more processors and/or hardwarecomponents, represented by one or more processors 1204, the receptioncomponent 1104, the configuration component 1106, the decoding component1108, the transmission component 1110, the RA component 1112, and acomputer-readable medium/memory 1206. The bus 1224 may also link variousother circuits such as timing sources, peripherals, voltage regulators,and power management circuits, etc.

The processing system 1214 may be coupled to a transceiver 1210, whichmay be one or more of the transceivers 254. The transceiver 1210 iscoupled to one or more antennas 1220, which may be the communicationantennas 252.

The transceiver 1210 provides a means for communicating with variousother apparatus over a transmission medium. The transceiver 1210receives a signal from the one or more antennas 1220, extractsinformation from the received signal, and provides the extractedinformation to the processing system 1214, specifically the receptioncomponent 1104. In addition, the transceiver 1210 receives informationfrom the processing system 1214, specifically the transmission component1110, and based on the received information, generates a signal to beapplied to the one or more antennas 1220.

The processing system 1214 includes one or more processors 1204 coupledto a computer-readable medium/memory 1206. The one or more processors1204 are responsible for general processing, including the execution ofsoftware stored on the computer-readable medium/memory 1206. Thesoftware, when executed by the one or more processors 1204, causes theprocessing system 1214 to perform the various functions described suprafor any particular apparatus. The computer-readable medium/memory 1206may also be used for storing data that is manipulated by the one or moreprocessors 1204 when executing software. The processing system 1214further includes at least one of the reception component 1104, theconfiguration component 1106, the decoding component 1108, thetransmission component 1110, and the RA component 1112. The componentsmay be software components running in the one or more processors 1204,resident/stored in the computer readable medium/memory 1206, one or morehardware components coupled to the one or more processors 1204, or somecombination thereof. The processing system 1214 may be a component ofthe UE 250 and may include the memory 260 and/or at least one of the TXprocessor 268, the RX processor 256, and the communication processor259.

In one configuration, the apparatus 1102/apparatus 1102′ for wirelesscommunication includes means for performing each of the operations ofFIG. 10. The aforementioned means may be one or more of theaforementioned components of the apparatus 1102 and/or the processingsystem 1214 of the apparatus 1102′ configured to perform the functionsrecited by the aforementioned means.

As described supra, the processing system 1214 may include the TXProcessor 268, the RX Processor 256, and the communication processor259. As such, in one configuration, the aforementioned means may be theTX Processor 268, the RX Processor 256, and the communication processor259 configured to perform the functions recited by the aforementionedmeans.

It is understood that the specific order or hierarchy of blocks in theprocesses/flowcharts disclosed is an illustration of exemplaryapproaches. Based upon design preferences, it is understood that thespecific order or hierarchy of blocks in the processes/flowcharts may berearranged. Further, some blocks may be combined or omitted. Theaccompanying method claims present elements of the various blocks in asample order, and are not meant to be limited to the specific order orhierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “one or more of A, B, or C,” “at least oneof A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or anycombination thereof” include any combination of A, B, and/or C, and mayinclude multiples of A, multiples of B, or multiples of C. Specifically,combinations such as “at least one of A, B, or C,” “one or more of A, B,or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and“A, B, C, or any combination thereof” may be A only, B only, C only, Aand B, A and C, B and C, or A and B and C, where any such combinationsmay contain one or more member or members of A, B, or C. All structuraland functional equivalents to the elements of the various aspectsdescribed throughout this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims. The words “module,” “mechanism,” “element,” “device,” andthe like may not be a substitute for the word “means.” As such, no claimelement is to be construed as a means plus function unless the elementis expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication of a userequipment (UE), comprising: receiving one or more configurations from abase station via signaling in a connected state; determining, based onthe one or more configurations, (a) resources of a first physicaldownlink control channel (PDCCH) indicating a first physical downlinkshared channel (PDSCH) that contains a random access message orindicating an uplink grant for transmitting a random access message and(b) resources of a second PDCCH; determining, in a time domain, (a) thatthe first PDCCH overlaps with the second PDCCH, (b) that the first PDCCHoverlaps with a second PDSCH that contains system data or user data andindicated by the second PDCCH, (c) that the first PDSCH overlaps withthe second PDCCH, or (d) that the first PDSCH overlaps with the secondPDSCH; determining that a first down-link reference signal formonitoring the first PDCCH and a second down-link reference signal formonitoring the second PDCCH are not quasi-colocated; and determiningthat monitoring the second PDCCH is an unexpected operation.
 2. Themethod of claim 1, wherein the first PDCCH overlaps with the secondPDCCH, the method further comprising: monitoring the first PDCCH; andrefraining from monitoring the second PDCCH.
 3. The method of claim 1,wherein the first PDCCH overlaps with the second PDSCH, the methodfurther comprising: monitoring the first PDCCH; and refraining fromdecoding the second PDSCH.
 4. The method of claim 1, wherein the firstPDSCH overlaps with the second PDCCH, the method further comprising:decoding the first PDSCH; and refraining from monitoring the secondPDCCH.
 5. The method of claim 1, wherein the first PDSCH overlaps withthe second PDSCH, the method further comprising: decoding the firstPDSCH; and refraining from decoding the second PDSCH.
 6. The method ofclaim 1, wherein the first PDCCH is scrambled with a random access radionetwork temporary identifier (RA-RNTI) and the second PDCCH is scrambledwith a radio network temporary identifier (RNTI) other than the RA-RNTI.7. The method of claim 1, wherein the first PDCCH is scrambled with atemporary cell radio network temporary identifier (TC-RNTI) and thesecond PDCCH is scrambled with a radio network temporary identifier(RNTI) other than the TC-RNTI.
 8. The method of claim 1, wherein thefirst PDCCH is located in a Type 1 PDCCH common search space set,wherein the second PDCCH is located in a Type 0 PDCCH common searchspace set, a Type 0A PDCCH common search space set, a Type 2 PDCCHcommon search space set, a Type 3 PDCCH common search space set, or a UEspecific PDCCH search space set.
 9. The method of claim 1, furthercomprising: determining that a random access event has occurred in theconnected state; selecting a down-link reference signal transmitted fromthe base station and that is not quasi-colocated with a serving beam offrom the base station to the UE; transmitting a preamble sequence to thebase station using random access sources indicating the selecteddown-link reference signal; and receiving, from the base station, therandom access message on the second PDSCH on a beam that is differentfrom the serving beam.
 10. The method of claim 1, wherein the firstdown-link reference signal is a channel state information referencesignal or a synchronization signal block.
 11. An apparatus for wirelesscommunication, the apparatus being a user equipment (UE), comprising: amemory; and at least one processor coupled to the memory and configuredto: receive one or more configurations from a base station via signalingin a connected state; determine, based on the one or moreconfigurations, (a) resources of a first physical downlink controlchannel (PDCCH) indicating a first physical downlink shared channel(PDSCH) that contains a random access message or indicating an uplinkgrant for transmitting a random access message and (b) resources of asecond PDCCH; determine, in a time domain, (a) that the first PDCCHoverlaps with the second PDCCH, (b) that the first PDCCH overlaps with asecond PDSCH that contains system data or user data and indicated by thesecond PDCCH, (c) that the first PDSCH overlaps with the second PDCCH,or (d) that the first PDSCH overlaps with the second PDSCH; determinethat a first down-link reference signal for monitoring the first PDCCHand a second down-link reference signal for monitoring the second PDCCHare not quasi-colocated; and determine that monitoring the second PDCCHis an unexpected operation.
 12. The apparatus of claim 11, wherein thefirst PDCCH overlaps with the second PDCCH, wherein the at least oneprocessor is further configured to: monitor the first PDCCH; and refrainfrom monitoring the second PDCCH.
 13. The apparatus of claim 11, whereinthe first PDCCH overlaps with the second PDSCH, wherein the at least oneprocessor is further configured to: monitor the first PDCCH; and refrainfrom decoding the second PDSCH.
 14. The apparatus of claim 11, whereinthe first PDSCH overlaps with the second PDCCH, wherein the at least oneprocessor is further configured to: decode the first PDSCH; and refrainfrom monitoring the second PDCCH.
 15. The apparatus of claim 11, whereinthe first PDSCH overlaps with the second PDSCH, wherein the at least oneprocessor is further configured to: decode the first PDSCH; and refrainfrom decoding the second PDSCH.
 16. The apparatus of claim 11, whereinthe first PDCCH is scrambled with a random access radio networktemporary identifier (RA-RNTI) and the second PDCCH is scrambled with aradio network temporary identifier (RNTI) other than the RA-RNTI. 17.The apparatus of claim 11, wherein the first PDCCH is scrambled with atemporary cell radio network temporary identifier (TC-RNTI) and thesecond PDCCH is scrambled with a radio network temporary identifier(RNTI) other than the TC-RNTI.
 18. The apparatus of claim 11, whereinthe first PDCCH is located in a Type 1 PDCCH common search space set,wherein the second PDCCH is located in a Type 0 PDCCH common searchspace set, a Type 0A PDCCH common search space set, a Type 2 PDCCHcommon search space set, a Type 3 PDCCH common search space set, or a UEspecific PDCCH search space set.
 19. The apparatus of claim 11, whereinthe at least one processor is further configured to: determine that arandom access event has occurred in the connected state; select adown-link reference signal transmitted from the base station and that isnot quasi-colocated with a serving beam of from the base station to theUE; transmit a preamble sequence to the base station using random accesssources indicating the selected down-link reference signal; and receive,from the base station, the random access message on the second PDSCH ona beam that is different from the serving beam.
 20. A computer-readablemedium storing computer executable code for wireless communication ofwireless equipment, comprising code to: determine, based on the one ormore configurations, (a) resources of a first physical downlink controlchannel (PDCCH) indicating a first physical downlink shared channel(PDSCH) that contains a random access message or indicating an uplinkgrant for transmitting a random access message and (b) resources of asecond PDCCH; determine, in a time domain, (a) that the first PDCCHoverlaps with the second PDCCH, (b) that the first PDCCH overlaps with asecond PDSCH that contains system data or user data and indicated by thesecond PDCCH, (c) that the first PDSCH overlaps with the second PDCCH,or (d) that the first PDSCH overlaps with the second PDSCH; determinethat a first down-link reference signal for monitoring the first PDCCHand a second down-link reference signal for monitoring the second PDCCHare not quasi-colocated; and determine that monitoring the second PDCCHis an unexpected operation.